Fix overread warnings #156
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GCC 11.2 differentiates between TYPE* abc and TYPE abc[] (cf. pmodels/mpich#5749). Therefore, we use the explicit pointer declaration to silence string overread warnings for GCC 11.2.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix overread warnings
Proposed changes:
char abc*instead of charabc[NUM]to avoid compiler warnings classified as string overread in case of strings that are shorter thanNUM - 1. These warnings appear because GCC 11.2 differentiates betweenTYPE* abcandTYPE abc[](cf. mpi: use pointers for array_of_statuses pmodels/mpich#5749).